docs: expand OpenAI-compatible endpoint recipes#563
Conversation
|
@OpenHands rebase this on main, please, and pay attention that the PR it was stacked on changed the number of the example then was merged |
|
I'm on it! enyst can track my progress at all-hands.dev |
Co-authored-by: openhands <openhands@all-hands.dev>
e76293e to
998ef46
Compare
|
Rebased this branch onto Validation run:
This comment was created by an AI agent (OpenHands) on behalf of the user. |
|
Since my last summary, there were no additional repository changes. Final status:
|
|
✅ Review complete. This review was performed through OpenHands Cloud Automation. You can log in and view the conversation here. |
all-hands-bot
left a comment
There was a problem hiding this comment.
Code Review
🟢 Good taste — This is a documentation expansion that significantly improves the OpenAI-compatible endpoint guide. The restructured content is clearer and the client recipes section is a valuable addition.
Summary
The PR expands the OpenAI-compatible endpoint documentation with:
- A restructured "What to Configure" + "Prepare a Profile" flow
- Client recipes for curl, Python SDK, JavaScript SDK, Chat UIs, and Voice/Webhook integrations
- A new "Conversation State" section explaining state management
- Cross-references added to overview pages and the SDK landing page
This is a documentation-only PR. The content is technically sound and the examples are accurate.
Minor Suggestions
🟡 Suggestion — [sdk/guides/agent-server/openai-gateway.mdx, lines 169-185] The Voice/Webhook code snippet references conversation_ids without showing its initialization. Consider adding a brief initialization example:
# conversation_ids: dict[str, str] = {}🟡 Suggestion — [sdk/guides/agent-server/openai-gateway.mdx, line 176] The Voice/Webhook example hardcodes model="openhands_gateway_demo" while other examples use the OPENHANDS_MODEL variable. For consistency, consider using the same pattern:
model=os.environ.get("OPENHANDS_MODEL", "openhands_gateway_demo")[RISK ASSESSMENT]
- [Overall PR]
⚠️ Risk Assessment: 🟢 LOW - This is a pure documentation change. No code, dependencies, or build configuration modified. Changes are additive documentation improvements with no breaking changes.
VERDICT:
✅ Worth merging — Documentation is well-written, accurate, and adds significant value. The minor suggestions are optional improvements.
KEY INSIGHT:
The new client recipes section with tabs is an excellent pattern that makes the documentation immediately actionable for users with different preferred tools.
This review was generated by an AI agent (OpenHands) on behalf of the user through OpenHands Automation. View conversation
|
@OpenHands please address the review and inline threads issues. Push the fixes. Then re-ask for the same bot review using gh api |
|
I'm on it! enyst can track my progress at all-hands.dev |
Co-authored-by: openhands <openhands@all-hands.dev>
|
✅ Review complete. This review was performed through OpenHands Cloud Automation. You can log in and view the conversation here. |
This comment was marked as duplicate.
This comment was marked as duplicate.
all-hands-bot
left a comment
There was a problem hiding this comment.
Code Review: PR #563 - docs: expand OpenAI-compatible endpoint recipes
Taste Rating: 🟢 Good taste
This PR significantly expands the OpenAI-compatible endpoint documentation with well-organized client recipes. The structure is clear and the content is technically sound.
Summary
The changes add comprehensive documentation for accessing the OpenHands agent-server via the OpenAI Chat Completions protocol, including:
- Configuration table at the top for quick reference
- Profile preparation with curl commands
- Client recipes for curl, Python SDK, JavaScript SDK, Chat UIs, and Voice/Webhook integrations
- Conversation state management explanation
- Current limitations clearly documented
No Critical Issues
This is documentation-only with no code changes, so standard critical issues (security, data structures, breaking changes) don't apply.
Minor Observations
- [sdk/guides/agent-server/openai-gateway.mdx] The diff appears truncated at "Ready-to-run example" — verify this section is complete and not cut off.
Good Patterns
- Clear, practical examples with real-world use cases (voice platforms, webhook integrations)
- Honest disclosure of current limitations (no streaming, no tool calls)
- Helpful cross-references to the new endpoint from overview docs
- The
<Tabs>component usage for client recipes is a good pattern for documentation
[RISK ASSESSMENT]
- [Overall PR]
⚠️ Risk Assessment: 🟢 LOW
Documentation-only changes. No security, breaking change, or data structure concerns. The new content adds value without introducing risk.
VERDICT:
✅ Worth merging: Documentation is well-structured, technically accurate, and provides practical value for users wanting to integrate OpenHands with OpenAI-compatible clients.
KEY INSIGHT:
The new client recipes (especially the Voice/Webhook integration pattern) will significantly reduce integration friction for users who want to connect OpenHands to existing OpenAI-compatible tooling.
This review was generated by an AI agent (OpenHands) on behalf of the user through OpenHands Automation. View conversation
Summary of changes
openhands_<profile_name>model naming,X-OpenHands-ServerConversation-IDstate handling, and current limitations (non-streaming, final text only, no OpenAI tool-call surface).Fixes OpenHands/software-agent-sdk#3540.
Validation:
docs.jsonand verifies modified MDX code fences, Tabs components, and local links are balanced/resolvable.This PR was created by an AI agent (OpenHands) on behalf of the user.
@enyst can click here to continue refining the PR